Storing user data in a service provider cloud without exposing user-specific secrets to the service provider

ABSTRACT

Subscriber (user) data is encrypted and stored in a service provider cloud in a manner such that the service provider is unable to decrypt and, as a consequence, to view, access or copy the data. Only the user knows a user-specific secret (e.g., a password) that is the basis of the encryption. The techniques herein enable the user to share his or her data, privately or publicly, without exposing the user-specific secret with anyone or any entity (such as the service provider).

BACKGROUND

Technical Field

This disclosure relates generally to encrypting and storing subscriberdata in a cloud storage environment in such a manner that a serviceprovider is restricted from decrypting and, as a consequence, fromaccessing, viewing or copying, that data.

Background of the Related Art

Remote access technologies, products and systems enable a user of aremote computer to access and control a host computer over a network.Internet-accessible architectures that provide their users with remoteaccess capabilities (e.g., remote control, file transfer, display screensharing, chat, computer management and the like) also are well-known inthe prior art. Typically, these architectures are implemented as aWeb-based “service,” such as LogMeIn, GoToMyPC, WebEx, Adobe Connect,Dropbox, and others. An individual (or subscriber) who uses the servicehas a host computer that he or she desires to access from a remotelocation. Using the LogMeIn service, for example, the individual canaccess his or her host computer using a client computer that runs webbrowser software.

An emerging information technology (IT) delivery model is cloudcomputing, by which shared resources, software and information areprovided over the Internet to computers and other devices on-demand.With this approach, an application instance can be hosted and madeavailable from Internet-based resources that are accessible over HTTPthrough a conventional Web browser. An example application is encrypteddata storage.

BRIEF SUMMARY

Subscriber (user) data is encrypted and stored in a service providercloud in a manner such that the service provider is unable to decryptand, as a consequence, to view, access or copy the data. Only the userknows a user-specific secret (e.g., a password) that is the basis of theencryption. The techniques herein enable the user to share his or herdata, privately or publicly, without exposing the user-specific secretwith anyone that is not an intended recipient of the data (such as theservice provider). The technique provides significant advantages becausethe end user password is never stored by the service providerpersistently; thus, the service provider cannot access the user's dataon its own. Using the described scheme, only upon receipt of the userpassword it is possible to decrypt and obtain an actual data key that isused (in the first instance) to encrypt the data itself. The data is notavailable in the clear in the service provider environment, andadditional mechanisms may be provided to facilitate sharing (bothprivate and public) while still maintaining the described securityparadigm.

In an embodiment, the user data is encrypted with a data key, such as asymmetric AES key. Any person or entity that possesses this data key candecrypt the customer data. Using the described technique, the data keyis hidden from unauthorized entities, which entities include the serviceprovider itself. To facilitate this goal, and as a further layer ofprotection, each user is assigned a public/private key pair, referred toas an account public key and its associated account secret key. RSA is arepresentative public/private key pair. The account public key is storedin a central database and is used to encrypt the data key that encryptsthe user data. The result of this encryption can only be decrypted withthe account secret key. According to the protection scheme, the accountprivate key is encrypted with the user-specific secret. Thus, if theuser wants to access the data, his or her user-specific secret (e.g.,the password) must be entered; as a result, the account secret key isobtained. The account secret key is then used to decrypt the data keythat decrypts the user data itself. This approach also facilitatessharing of the user data (with a person or entity authorized by theuser) in a secure manner.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and theadvantages thereof, reference is now made to the following descriptionstaken in conjunction with the accompanying drawings, in which:

FIG. 1 depicts an extensible Web-based remote access architecture inwhich exemplary aspects of the file transfer method may be implemented;

FIG. 2 is a process flow illustrating a method of storing and protectinguser data in a service provider cloud according to this disclosure;

FIG. 3 depicts a UML interaction diagram for end user account managementto the service provider cloud;

FIG. 4A and FIG. 4B together depict a UML interaction diagram ofrepresentative host computer interactions with the service providercloud; and

FIG. 5 depicts a UML interaction diagram of representative serviceprovider website interactions.

DETAILED DESCRIPTION OF AN ILLUSTRATIVE EMBODIMENT

By way of background, FIG. 1 illustrates a high level view of a remoteaccess architecture 100 in which the disclosed technique may bepracticed. This architecture is merely representative, and it should notbe taken as limiting. Preferably, the architecture comprises “n-tiers”that include a web server tier 102, a database tier 104, and a gatewaytier 106. The web server tier 102 comprises a plurality of machines thateach executes web server software. The web server tier provides anInternet-accessible web site. Preferably, the web site associated with asite domain (however designated) is available from multiple locationsthat collectively comprise the web server tier 102. The database tier104 comprises a plurality of machines that each executes database serversoftware. The database tier provides a network-accessible data storageservice for generating and storing data associated with end usersessions to the remote access service. The gateway tier 106 comprises aplurality of machines that each executes application server software.The gateway tier provides a network-accessible connection service forestablishing and maintaining connections between and among theparticipating end user computers. Although not shown, preferably enduser machines connect to the gateway servers over secure connections,e.g., over SSL, TLS, or the like. A representative machine on which theweb server, database server or gateway server executes comprisescommodity hardware (e.g., one or more processors) running an operatingsystem kernel, applications, and utilities. Typically, the tiers aremanaged and operated by a commercial service provider, such as LogMeIn®,of Woburn, Mass. The service provider may have additional cloud-basedinfrastructure, such as cloud storage, but this is not required. Cloudstorage may be provided by a third party entity. The service providerhas an associated central database in which cryptographic keys andassociated data may be stored.

As also seen in FIG. 1, the “user” of the remote access servicetypically has at least two (2) distinct machines associated therewith. Afirst machine, referred to as a “host” 103, is a machine that hasresources (e.g., services, applications, files, or the like) that aredesired to be accessed remotely from a second machine, referred to asthe “client” 101. The host, which is Internet-accessible, includes aremote access “host” application. The host has an associatedcryptographic data store, which is a secure (protected) data store forstoring cryptographic materials such as keys and associated data. Theclient machine also is an Internet-accessible machine that typicallyincludes a web browser or similar rendering engine. A representativemachine is a laptop computer, or a mobile device, such as a smartphoneor tablet (e.g., the iPhone® or iPad®). Generalizing, the mobile deviceis any wireless client device, e.g., a cellphone, pager, a personaldigital assistant (PDA, e.g., with 3G or higher NIC), a mobile computerwith a smartphone client, or the like. Other mobile devices include anyaccess protocol-enabled device (e.g., a Blackberry® device, anAndroid™-based device, or the like) that is capable of sending andreceiving data in a wireless manner. The first machine includes a remoteaccess client application. In the case of a mobile device, the remoteaccess client application may be LogMeIn Ignition™. The clientapplication may be downloaded and installed via a mobile applicationdelivery service, such as the Apple® App™ Store.

As used herein, the following terms have the following meanings:

A “user_password” is a user-specific secret (or “password”) of anauthorized user's account. A goal of the technique herein is that thissecret is only known by the authorized user and remains unknown to theservice provider. As will be seen, this “user password” is used toencrypt and decrypt the account secret key.

The “user_data” is content (or, more generally, data) that theauthorized user desires to be encrypted and stored in the serviceprovider's cloud storage.

The “aes_data_key” is a cryptographic key, such as a 256-bit symmetricAES key, that is used to encrypt the user_data desired to be encryptedand stored in the cloud storage.

The “enc_file” is a file generated by encrypting, with the aes_data_key,the user_data. Thus, enc_file results from an encryption function,designated herein by the following: encrypt (user_data, aes_data_key).This is the encrypted “file” as it is stored in the cloud storage.

An account of an authorized user has a key pair associated therewith.Preferably, the key pair is generated using a public key cryptographicprotocol such as RSA. The public key of the RSA public/private key pairis designated herein as rsa_pub_acc_key, and the associated private (or“secret”) key is designated herein as rsa_priv_acc_key. The public keyis the “account public key” and the private key is its associated“account secret key.” Typically, the account public key is stored in thecloud service provider central database, as well as in the hostcryptographic data store. The account secret key is stored in the hostcryptographic data store.

As will be seen, and according to the disclosed technique, the accountsecret key for the authorized user is encrypted with the authorizeduser's user-specific secret (password), i.e., encrypt (rsa_priv_acc_key,PBKDF (user_password)), with the result being a “value” enc_acc_key thatis preferably stored in the service provider central database.

The data key aes_data_key is encrypted with the account public keyrsa_pub_acc_key as follows: rsa_encrypt (aes_data_key, rsa_pub_acc_key).The resulting “account encrypted data key” preferably is stored in theservice provider central database, and in the host cryptographic datastore.

The pub_enc_data_key is the data key aes_data_key encrypted with a tokenassociated with a public link, as rsa_encrypt (aes_data_key,PubliLinkToken), and it is stored in the service provider centraldatabase.

FIG. 2 illustrates a process flow of a method of storing and protectinguser data in a service provider cloud of this disclosure. The serviceprovider may be a standalone commercial service provider (such asLogMeIn, or the like), or any other cloud-based environment, such as anenvironment created from existing IT infrastructures that are adapted tosupport cloud-based services. In general, a representative cloudcomputing environment comprises a set of front-end administrative andoperational support functions, together with a set of back-endcomputational resources. Typically, the cloud compute resources comprisea set of virtual machine instances (which are used to execute a targetapplication that is being made available for access via the cloud), datastores, and associated support services. In an alternative embodiment,the subscriber stores data on one or more machines that are owned orcontrolled by the subscriber.

The process begins at step 200. The end user registers to the service atstep 202 and, as an authorized user, obtains an account. Thereafter, atstep 204, a key pair is associated with the account of the authorizeduser. The key pair comprises an account public key, and an associatedaccount secret key. Preferably, the key pair is an RSA public/privatekey pair, although this is not a limitation. At step 206, the authorizeduser is provided the account secret key. Preferably, the communicationof the account secret key to the end user occurs over a secure transportchannel (e.g., an SSL link). This is not a limitation, as the accountsecret key may be provided via other means, such as e-mail, instantmessage, text message, or the like. At step 208, the service providerreceives and stores a “value” that has been generated (within thecontext of the end user machine) by encrypting the account secret keywith a user-specific secret. The user-specific secret is known only tothe end user. This completes the basic provisioning operations that arenecessary to facilitate described security method.

The process then continues with securing and storing the end user data(or content). In particular, at step 210, data (desired to be protected)associated with the authorized user is encrypted with a data key toproduce a “file.” This operation takes place in association with or atthe end user machine. At step 212, the file (that has been generated byencrypting with the data key data associated with the authorized user)is received and stored in the service provider cloud. The serviceprovider also receives the data key. At step 214, the service providerencrypts the data key (received at step 212) with the account public keyto generate an account encrypted data key, which the service providerthen stores. This completes the storage operations.

To provide access to the data, the process continues. In particular, atest is performed at step 216 to determine whether the user-specificsecret has been entered (and received). If not, the routine cycles. If,however, the outcome of the test at step 216 indicates receipt of theuser-specific secret, the routine continues. At step 218, the serviceprovider decrypts the value (received at step 208) to recover theaccount secret key. At step 220, the service provider then uses theaccount secret key (which it just recovered) to decrypt the accountencrypted data key (which was generated at step 214) to recover the datakey itself. At step 222, the service provider then decrypts the file(which had been received at step 212) stored in the service providercloud with the (just recovered) data key. Once the file is decrypted,the “data” is then provided at step 224. This completes the process.

Thus, the described technique enables user data to be stored (as anencrypted “file”) in a service provider cloud without exposing theuser-specific secret to the service provider.

FIG. 3 is a UML interaction diagram illustrating representativeinteractions among a host browser 300, a service provider front-end webserver 302, and a service provider back-end database 304. The describedfunctions include a Register Account function 306, a Change Passwordfunction 308, and a Lost Password function 310. The Register Accountfunction 306 is the technique used by an end user to obtain anauthorized user account, as described above. This function associatesthe RSA key pair with the account, as has been described. The relevantaccount data (for the authorized end user and his or her account) isthen stored in the database. The user password itself, however, is notstored persistently by the service provider (although it is availablein-memory as needed). Rather, the database stores enc_acc_key (thevalue), rsa_pub_acc_key (the account public key) and the user's e-mailaddress (or other identifier). The end user may change his or herpassword using the Change Password function 308 as illustrated but, onceagain, the new password is never stored in the database 304. Rather,only the value is updated and stored. In addition, in the event the enduser loses or forgets his or her password, the security model enablesthe Lost Password function 310 to enable the end user to create andenable use of a new password; however, once again the new password isnot stored in the database. Rather, only the value gets updated.

FIG. 4 is a UML interaction diagram illustrating representativeinteractions among a first host 400, a service provider data centermachine 402, a second host 404, and an associated browser 406. Each ofthe first and second hosts 400 and 404 operate a remote accessapplication provided by the service provider. Each host also includes acryptographically-secure data store (or “crypto-store”). In this examplescenario, the browser 406 executes on a client machine of a third party,and the third party may or may not be a subscriber to the service butwill be invited to access or view data associated with an authorizeduser account. If the third party is a subscriber, typically he/she willhave an associated host, which in this example corresponds to the secondhost 404. Each host machine has its own associated public/private keypair with the service provider.

As illustrated, the described functions include a Register Host function408, a Join/Create Sync Set function 410, a Host Put Data function 412,a Host Get Data function 414, a Host Share function 416, and an AcceptInvite function 418. The Register Host function 408 is used to registerthe host machine with the service provider. As a result, the serviceprovider provides various pieces of information to the host includingthe account public key, the account secret key, and a host identifier,which the host then stores in the associated crypto-store. TheJoin/Create Sync Set function 410 is the function by which the hostmakes a request to the service provider to create a new synchronizationset or to join an existing synchronization set (as stored in the cloudor other data storage). Typically, a “sync” set is created whenever itis desired to have a data set stored in the cloud and then replicatedacross one or more additional hosts for data integrity purposes. Inother words, synchronization performs replication of the file across aset of machines. The synchronization process is implemented using adistributed real-time file synchronization application that ensuresselected folders always have identical content on all participatingcomputers. This application is merely illustrative, as the techniquedescribed herein may be used to secure any subscriber data on one ormultiple machines.

Using the Join/Create Sync Set function 410, the host obtains theaccount secret key, which it saves in the associated crypto-store. Thisis step 206 in FIG. 2. The Host Put Data function 412 is used to storethe subscriber data in the cloud, as previously described. This functioncorresponds to steps 210 and 212 in FIG. 2. The file is stored by thehost making an HTTP PUT request. The Host Get Data function 414 is usedto enable the host machine to obtain access to data from storage. Tothis end, the host makes an HTTP GET request to the data center, passingin the name of the file. The file is returned to the host, which thenperforms the identified decryption operations to obtain access to theuser data. The Host Share function 416 is used to enable the host togenerate an invitation (and, in particular, an invitation link) toaccess the user data and to send that invitation to the client browser406. The invitation link includes a temporary password that ispreferably a one-time use password. The client browser 406 executes theAccept Invite function 418 to obtain access to the user data by theinvitee clicking on the invitation link. If the invitee is not a user ofthe service, the new user is first directed to register with theservice, after which a password change is effected to substitute theinvitee's password for the temporary password. The invitee then obtainsand stores (in its associated host 404 crypto-store) the key informationthat is necessary to enable acceptance of the (first) user's shareinvitation.

FIG. 5 is a UML interaction diagram illustrating representativeinteractions among a client browser 500, the service provider web server502, and the server provider back-end database 504 to facilitate publicaccess to the user data. An Access function 506 is the operation bywhich the end user obtains access to his or her data that has beenstored (and possibly replicated by the distributed synchronizationapplication). To this end, the end user logs into the service andprovides the user-specific secret, namely, the user password that is notstored in the service provider database. Steps 222 and 224 (of FIG. 2)are then carried out to enable the browser to obtain access to thedesired user data. The Public Link function 508 provides an alternativetechnique by which the browser can request and obtain a public linktoken (or “ticket”) that can be shared and used to access the user data.

The above-described technique provides significant advantages. Becausethe end user password is never stored persistently by the serviceprovider, the service provider cannot access the user's data on its own.Only upon receipt of the user password it is possible to decrypt andobtain the data key that is used (in the first instance) to encrypt thedata itself. The data is not available in the clear in the serviceprovider environment, and additional mechanisms are provided tofacilitate sharing (both private and public) while still maintaining theabove-described security paradigm. When access to the end user data isrequired, the user password is available (but only in-memory), thusensuring that the user-specific secrets are never exposed to the serviceprovider.

Variants

With suitable security in place, it may be desirable to generate the keypair (the account public key and the associated account secret key) onthe client.

The encrypting of the account secret key with the user password mayinvolve additional steps. Thus, in the case where it is desired to useshorter key lengths on the client, the account secret key may beencrypted first using a shorter key length AES key, with the resultbeing encrypted by the user password.

In appropriate circumstances, such as where the unauthorized user onlyaccesses his or her files via the Web, it is not necessary to providethe authorized user (or any software being run thereby) with the accountsecret key.

While the above describes a particular order of operations performed bycertain embodiments of the invention, it should be understood that suchorder is exemplary, as alternative embodiments may perform theoperations in a different order, combine certain operations, overlapcertain operations, or the like. References in the specification to agiven embodiment indicate that the embodiment described may include aparticular feature, structure, or characteristic, but every embodimentmay not necessarily include the particular feature, structure, orcharacteristic.

While the disclosed subject matter has been described in the context ofa method or process, the subject disclosure also relates to apparatusfor performing the operations herein. This apparatus may be speciallyconstructed for the required purposes, or it may comprise ageneral-purpose computer selectively activated or reconfigured by acomputer program stored in the computer. Such a computer program may bestored in a computer readable storage medium, such as, but is notlimited to, any type of disk including an optical disk, a CD-ROM, and amagnetic-optical disk, a read-only memory (ROM), a random access memory(RAM), a magnetic or optical card, or any type of media suitable forstoring electronic instructions, and each coupled to a computer systembus.

While given components of the system have been described separately, oneof ordinary skill will appreciate that some of the functions may becombined or shared in given instructions, program sequences, codeportions, and the like.

Having described our invention, what we now claim is as follows.
 1. Amethod to store and protect user data in a service provider cloud,comprising: storing a value that has been generated by encrypting anaccount secret key with a user-specific secret, the value being distinctfrom an account public key and the associated account secret key, theaccount secret key and the account public key comprising a key pairuniquely associated with an account of an authorized user; storing afile that has been generated by encrypting data associated with theauthorized user with a data key; storing an account encrypted data key,the account encrypted data key having been generated by encrypting thedata key with the account public key; generating an invitation link thatenables access to the file, that invitation link including a one-timepassword; and providing access to the data associated with theauthorized user upon receipt of the user-specific secret or the one-timepassword by the following ordered operations executed in a computingmachine having a hardware element: (i) decrypting the value to obtainthe account secret key, then (ii) decrypting, using the account secretkey so obtained, the account encrypted data key to obtain the data key,then (iii) decrypting, using the data key so obtained, the file.
 2. Themethod as described in claim 1 wherein the key pair is generated on aclient device associated with the authorized user.
 3. The method asdescribed in claim 1 wherein the data key is a symmetric key.
 4. Themethod as described in claim 1 wherein the key pair is an RSApublic/private key pair.
 5. The method as described in claim 1 theaccount secret key is encrypted using a key prior to encryption with theuser-specified secret.
 6. The method as described in claim 5 wherein thekey is an AES key.
 7. The method as described in claim 1 furtherincluding providing the account secret key to the authorized user. 8.The method as described in claim 1 wherein the service provider cloud isoperated by a remote access service provider.
 9. The method as describedin claim 1 wherein the user-specific secret only is retained in-memoryin the service provider cloud and not persisted to disk.